<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://www.modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/6756/Tariffs-Reloaded-What-Trumps-2025-Trade-Agenda-Teaches-Business-Analysts-About-Strategic-Friction.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6756</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6756&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Tariffs Reloaded: What Trump’s 2025 Trade Agenda Teaches Business Analysts About Strategic Friction</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/6756/Tariffs-Reloaded-What-Trumps-2025-Trade-Agenda-Teaches-Business-Analysts-About-Strategic-Friction.aspx</link> 
    <description>Tariffs are not just economic instruments&amp;mdash;they&amp;rsquo;re strategic signals. For business analysts, Trump&amp;#39;s latest trade measures are more than policy&amp;mdash;they&amp;rsquo;re a masterclass in navigating disruption, identifying leverage, and transforming systemic friction into strategic insight.
</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Mon, 26 May 2025 22:44:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6756</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/637/Handling-Requirements-Effectively-on-Agile-Projects.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=637</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=637&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Handling Requirements Effectively on Agile Projects</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/637/Handling-Requirements-Effectively-on-Agile-Projects.aspx</link> 
    <description>Why has it been necessary to write so many different, book-length treatises about requirements management on software projects? Is it not possible to develop an approach to handling software requirements that is simple enough to express concisely -- and yet can work with large, complex projects as well as smaller efforts? 

At the risk of using a word that disturbs many in the field of software engineering, requirements management is just a process. The more simply this process can be described, the more likely it will be to work in real software organizations. So rather than consider every possible nuance relating to managing software requirements, this article will attempt to express the essence of an approach that can work well on virtually any Agile software development project. In the appendix, I include a detailed example illustrating the key ideas.
Author: Theodore F. Rivera, Software Group Strategist, IBM</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 23 Dec 2008 08:54:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:637</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/477/Tracing-Corporate-Strategy-to-a-Line-of-Code.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=477</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=477&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Tracing Corporate Strategy to a Line of Code</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/477/Tracing-Corporate-Strategy-to-a-Line-of-Code.aspx</link> 
    <description>One of the issues high on the agenda of many CIOs is to align IT efforts with the company&amp;rsquo;s strategic goals. But how you do trace a line of code back to the strategic goal that caused it to be written? If we&amp;rsquo;re able to do this then, and only then, can it be said that IT is aligned with the business strategy.&amp;nbsp;
</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 08 Jul 2008 02:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:477</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/443/How-vulnerable-are-you-A-crash-course-in-software-security.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=443</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=443&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How vulnerable are you? A crash course in software security</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/443/How-vulnerable-are-you-A-crash-course-in-software-security.aspx</link> 
    <description>Software security remains a hot topic. Everyone from grandmothers to Fortune 500 companies has heard the stories of identity theft, data loss, and general mayhem caused by viruses and attackers on the Internet. In the first quarter of 2008 alone, 1,474 different software vulnerabilities were reported with only 64 of them having posted solutions. That&#39;s a resolution rate of about 4%. With all the buzz about software and system security, the computer world may seem to be in total chaos, leading many to ask, &quot;How vulnerable am I?&quot; 

In this article I present some of the results of a recent security project at Worcester Polytechnic Institute (WPI), along with additional research. My intention is to demonstrate what software security is by demystifying common terminology and providing realistic examples of typical security exploits. 

This article is not intended to provide a comprehensive computer security education, but rather to serve as an introduction to some of the key topics in the vast and expanding field of information security.
Author: Bob Breznak</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Thu, 15 May 2008 06:04:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:443</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/226/10-signs-you-arent-cut-out-to-be-a-systems-analyst.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=226</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=226&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>10 signs you aren&#39;t cut out to be a systems analyst</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/226/10-signs-you-arent-cut-out-to-be-a-systems-analyst.aspx</link> 
    <description>The Bureau of Labor Statistics predicts that job opportunities for systems analysts will increase at an above-average pace through 2014, as organizations continue to build and implement increasingly complex technologies. 

If you&#39;ve been wondering whether you&#39;d be happy in the role of systems analyst, take a look at the following list. If you see yourself in some of these descriptions, you might want to consider another career route.&amp;#160;
Author: Suzanne Thornberry</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Mon, 21 Jan 2008 06:29:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:226</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/89/A-Systems-Analysts-Career-Useful-Technologies-Tasks-and-Traits.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=89</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=89&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>A Systems Analyst’s Career: Useful Technologies, Tasks, and Traits</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/89/A-Systems-Analysts-Career-Useful-Technologies-Tasks-and-Traits.aspx</link> 
    <description>Systems analysts research, plan, and recommend software and system choices to meet their client organizations&amp;rsquo; business requirements. Systems analysts primarily function as links between vendors and organizations. They develop cost analyses, system designs, and implementation schedules. They also study the feasibility of computer systems before recommending them to management.
Author: Roshan Tolani</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Fri, 14 Sep 2007 03:33:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:89</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/36/So-You-Want-To-Be-a-Requirements-Analyst.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=36</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=36&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>So You Want To Be a Requirements Analyst?</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/36/So-You-Want-To-Be-a-Requirements-Analyst.aspx</link> 
    <description>Be it explicitly or not, someone always performs the role of requirements analyst on a software project. The official title may be requirements engineer, business analyst, system analyst, product manager, or simply analyst , but someone needs to translate multiple perspectives into a requirements specification and communicate with other stakeholders.
Perhaps most importantly, the analyst helps determine the difference between what customers say they want and what they really need&amp;mdash;and that&amp;rsquo;s easier said than done.
Author: Karl Wiegers</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Mon, 04 Jun 2007 22:43:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:36</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/10/Using-UML-Activity-Diagrams-for-the-Process-View.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=10</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=10&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Using UML Activity Diagrams for the Process View</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/10/Using-UML-Activity-Diagrams-for-the-Process-View.aspx</link> 
    <description>In this article, the focus shifts to a particular view in the 4+1 Architecture Views, defined by the Rational Unified Process. We will examine how to use Activity Diagrams as &quot;roadmaps&quot; for the Process View, to capture processing flows as a series of steps. We will also discuss several techniques for creating these diagrams and ensuring their effectiveness.
Author: Ben Lieberman</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 01 May 2007 17:54:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:10</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/8/UML-Activity-Diagrams-Versatile-Roadmaps-for-Understanding-System-Behavior.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=8</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=8&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML Activity Diagrams: Versatile Roadmaps for Understanding System Behavior</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/8/UML-Activity-Diagrams-Versatile-Roadmaps-for-Understanding-System-Behavior.aspx</link> 
    <description>The core purpose of software development is to provide solutions to customers&#39; real problems. Use cases are a vital aspect of a technique that has been used successfully to ensure that development projects actually focus on these problems. They are used to discover, capture, and present customer requirements in a form that is accessible to developers, testers, and other stakeholders in a development project. To detail a use case, it is critical to capture basic, alternate, and exceptional flows of execution, which represent major and minor threads of execution the system encounters as it processes customer requests.
Using the &quot;standard&quot; use-case form, these flows can be captured using plain English to describe sequential activities. These descriptions are quite detailed, however, and they can be difficult to decipher -- especially within a complex set of use-case scenarios.
This article describes another way to capture these flows: by using Unified Modeling Language (UML) Activity Diagrams that depict the flows as &quot;roadmaps&quot; of system functional behavior. These roadmaps are analogous to AAA (Automobile Association of America) roadmaps, in that they show what routes you can take but do not indicate whether you will take them.
An AAA map, moreover, supplies only enough information to identify locations of interest, leaving detailed descriptions of the road for companion travel guides. Similarly, Activity Diagrams show a comprehensive summary of use-case flows but leave the design details up to other artifacts.
We will also take a brief look at other ways to use Activity Diagrams during the development lifecycle.
Author: Ben Lieberman</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 01 May 2007 17:46:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:8</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/6/UML-Activity-Diagrams-Detailing-User-Interface-Navigation.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML Activity Diagrams: Detailing User Interface Navigation</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/6/UML-Activity-Diagrams-Detailing-User-Interface-Navigation.aspx</link> 
    <description>The author illustrates how to use UML Activity Diagrams to capture and communicate the details of user interface navigation and functionality, and explain three stereotypes: presentation, exception, and connector. 
Author: Ben Lieberman</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 01 May 2007 17:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/11/Five-Things-IT-Managers-Should-Know-About-Software-Requirements.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=11</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=11&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Five Things IT Managers Should Know About Software Requirements</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/11/Five-Things-IT-Managers-Should-Know-About-Software-Requirements.aspx</link> 
    <description>Some days, you wish you had telepathy. You just know that your development staff is holding back in some way, but you don’t know how to get them to communicate. Is the project in trouble, but they’re afraid to tell you? 
Since your software development staff won’t tell you what they’re really thinking, I asked them to confide in us instead. I posed a single question to professional programmers and testers: If you could get your CIO to understand just one thing about software requirements, what would it be? From the answers, I collated the five things at the top of their minds. If you grok these concepts, you will win the respect and support of your programming department (prizes you’ll also earn for understanding the term &quot;grok&quot;), and you’ll optimize the chance of success for your next software project.
I must warn you that this will shock some developers. Most of them don’t expect you to have a clue.
Author: Esther Schindler</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Tue, 06 Mar 2007 19:18:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:11</guid> 
    
</item>
<item>
    <comments>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/12/UML-RUP-and-the-Zachman-Framework-Better-together.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://www.modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=12</wfw:commentRss> 
    <trackback:ping>https://www.modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=12&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>UML, RUP, and the Zachman Framework: Better together</title> 
    <link>https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/12/UML-RUP-and-the-Zachman-Framework-Better-together.aspx</link> 
    <description>This article proposes innovative ways to combine three of the most important methodologies that have emerged in the past decade in the field of information systems architecture: UML, RUP, and the Zachman Framework. 
Over the past decade, the advantages of using the Unified Modeling Language (UML) for modeling software applications have become clear. During this same timeframe, the Rational Unified Process, or RUP, has proved itself as a software development process, and the Zachman Framework has proved itself as a framework for organizing and communicating architectural artifacts. Amid the swarm of overlapping methodologies, these stand apart as three pillars of modern information systems architecture. This article considers the combined usages of these technologies by examining their meta-characteristics and proposing some ways to apply them in combination within organizations.
Author: Vitalie Temnenco</description> 
    <dc:creator>host</dc:creator> 
    <pubDate>Fri, 02 Mar 2007 18:32:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:12</guid> 
    
</item>

    </channel>
</rss>